home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
dskut
/
combi113.zip
/
README
< prev
next >
Wrap
Text File
|
1993-05-03
|
23KB
|
558 lines
COMBI-Disk -
RAM disk & disk cache
Preface.
--------
- Why don't You use disk cache?
- I'd like, but memory constrains prevent me from using it:
I need more memory for RAM disk.
-----
- Why don't You use RAM disk?
- I'd like, but memory constrains prevent me from using it:
I need more memory for disk cache.
-----
- Why don't You use RAM disk or disk cache?
- I'd like, but some of my applications require free extended
memory.
If one of these answers is Yours then COMBI-Disk is for You!
You may hit THREE targets with a single shot - installing COMBI-Disk
You get a RAM disk and a Disk-Cache and free XMS memory at the same
time in the SAME area of extended memory!
When You install COMBI-Disk You specify amount of extended memory for
it and You get a RAM disk of the specified size and a Disk-Cache of the
same size. You may also specify amount of memory which should be
released if some program requires it. Then when You work with Your PC,
You enjoy COMBI's disk cache which is not worse than others (I hope it
is better). Suppose now that You start a program which needs a disk
buffer for temporary storage and tell it to use RAM disk. Then the
program may use the whole amount of the RAM disk's space (though
contracting the size of cache). When it terminates and deletes
temporary files You get back your cache buffer! If a program requests
XMS memory COMBI-disk may loan some of its memory to the program (if it
has the requested amount free of RAM disk data). When the program
releases the memory COMBI-disk reallocates it back.
I've been reported of 25% increase in compilation speed with COMBI
compared to that for other cache programs. Sure, the starting conditions
were different: with COMBI the source files were put on the RAM disk
and the compiler (BCX.EXE) used XMS memory released by COMBI. In fact,
one could, probably, achieve the same performance installing a RAM disk
and setting cache size so that there is enough free XMS not used by either
RAM disk or disk cache. But how would one calculate the optimal size of
RAM disk and free XMS? And that is not very convenient to reconfigure
(and reboot) system depending on what task are You going to deal with.
Applications.
------------
Some programs (e.g. compilers, word-processors etc.) need a buffer for
temporary storage, and if the storage is RAM disk then their performance
may be increased few times compared with the case of usage of hard disk
instead. That's why You may sometimes need a RAM disk. But if You use
standard RAM disk (Microsoft (C) RAMDRIVE.SYS or IBM (C) VDISK.SYS or any
other) it often comes out that it stays empty most of the time though
consuming Your extended (expanded) memory. That's why You may wish to
give up using RAM disk or make it less in order to have more memory
for disk cache which is always useful.
Moreover, some of programs can take advantage of XMS memory if it is
available. That's why You may wish to give up using disk cache (though
some of caches support memory reallocation without reinstallation).
Don't get disappointed!
COMBI-Disk
is a nice solution of this problem! It uses a little more memory for
RAM disk than is needed to keep all files written into it while all the
remaining memory is used for cache. You need not bother to make this
memory larger - just WRITE Your file(s) into RAM disk, all the rest it
does itself! You need not bother as well to contract RAM disk's size
and increase cache size - just DELETE files from RAM disk and all the
released memory will be used for cache! You need not bother to
reconfigure Your system when You need some free XMS memory - COMBI-disk
takes care of that itself (however, if You forgot to specify amount of
memory COMBI-disk would release, You have to run COMBI control program
to tell COMBI-disk that You need certain amount of free XMS memory).
System requirements.
-------------------
1. 80x86 based machine with extended memory.
2. DOS 3.30+.
3. Extended memory manager which supports XMS 2.0 specifications
which supports "reallocate XMS" function (Microsoft (C) HIMEM.SYS
ver 2.77+ or Quarterdeck (C) QEMM.SYS will do, as well as most
others).
General features.
----------------
- COMBI-disk may use up to 16 Mbytes of extended (XMS) memory.
- Up to 8 physical hard disks are supported.
- Starting from version 1.00 background write caching is
supported.
- Automatic reallocation of XMS memory.
- Variable size of cache block (memory allocation unit) -
from 1 to 8 disk sectors (512 bytes each).
- IOCtl interface to control program.
- HMA may be used for COMBI-disk data tables (even when MS-DOS
5.0 is loaded into HMA and under DR-DOS 6.0 as well).
Installation.
------------
WARNING! It is recommended to make backup of hard disk before
installation of COMBI-disk (as well as any other disk cache program).
COMBI-Disk installation process is quite straightforward, although it
requires some tweaking with the contents of your CONFIG.SYS file. Copy
COMBI.SYS into Your hard-disk and insert the following line into Your
CONFIG.SYS file
DEVICE=[drive:][path]COMBI.SYS [<parameters>]
The proper place in CONFIG.SYS would be after all memory managers,
after disk managers and if possible before disk write-protection
programs (otherwise You should not turn on write caching).
The <parameters> are all optional and include:
[<buff_size> [<rls_size>]] [/V [<RAMd_parms>]] [/C [<cache_parms]] [/H] [/Q]
<buff_size> - the amount of XMS memory (Kbytes) You want to use for
COMBI-Disk. Minimum is 128K, maximum is about 14000K.
If it is omitted then all available memory is default.
There is no harm if You specify more memory than really is
available - then COMBI-disk uses all available memory.
<rls_size> - maximum number of XMS memory (Kbytes) COMBI-disk should
release when it is requested. Default is all available.
If You want to ensure that there always is some memory
available for RAM disk You may specify this size to be
less than COMBI allocates for its buffers. Note, if You
want to specify this number You should also specify
<buff_size>.
/V - means that RAM disk parameters follow.
<RAMd_parms> - RAM disk parameters may be the following:
F:<disk_size>- specifies formatted size of RAM disk. By default COMBI
creates RAM disk of the size (<buff_size> - <min_cache>)
Kbytes. But You may specify a less size.
R:<root_num> - number of entries in root directory of RAM disk. Default
is 64. If You encounter DOS error "can't create file..."
when number of file in root directory is 63 (plus one
for volume label) then try specifying, say, R:128.
S:<sect_size>- sector size for RAM disk - 256 or 512 bytes, default is
512 bytes. Using 256 bytes sectors may sometimes save
some space on RAM disk but this is effective only if
RAM disk size is less than 1 Mbyte.
N - tells RAM disk not to return 'sector not found' error
(see also below). This setting may be always changed by
control program.
/C - means that cache parameters follow.
<cache_parms>- cache parameters may be the following:
M:<min_cache>- specifies minimum cache size (Kbytes). This reduces size
of RAM disk but guarantees that specified amount of
memory will be always allocated to cache. Default is 0.
U:<block_sec>- number of sectors per cache block (from 1 to 8). Using
smaller blocks may result in more effective usage of
memory (if You have not much of it) but leads to slower